Skip to content

Expose vector store search capabilities and enforce supported search modes - #74

Merged
spelech merged 6 commits into
mainfrom
fix/search-expose-backend-capabilities-10161170291051937970
Oct 28, 2026
Merged

spelech merged 6 commits into
mainfrom
fix/search-expose-backend-capabilities-10161170291051937970

Conversation

@spelech

@spelech spelech commented Oct 27, 2026

Copy link
Copy Markdown
Owner

Exposed search capabilities across vector store backends (Qdrant, Chroma, PgVector), validated search modes to reject unsupported modes (e.g. lexical search on dense-only backends), mapped default hybrid mode to semantic on dense-only stores, and updated SearchInspector UI and test suites.

Fixes #56


PR created automatically by Jules for task 10161170291051937970 started by @spelech

- Add get_capabilities() to VectorStore base class and implementations in QdrantVectorStore, ChromaVectorStore, and PgVectorStore.
- Include capabilities in stats and vector store config API payloads.
- Explicitly reject unsupported search modes (e.g. lexical on Chroma or pgvector) with ValueError and ensure true lexical search does not invoke dense embedding calls.
- Gracefully map default hybrid search requests to semantic search on dense-only vector stores.
- Update SearchInspector UI component to fetch backend capabilities and gate search mode buttons and weighting controls accordingly.
- Add backend-specific test coverage for capability reporting, search mode validation, and dense/lexical/hybrid behavior across Qdrant, Chroma, and PgVector.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

- Add get_capabilities() to VectorStore base class and implementations in QdrantVectorStore, ChromaVectorStore, and PgVectorStore.
- Include capabilities in stats and vector store config API payloads.
- Explicitly reject unsupported search modes (e.g. lexical on Chroma or pgvector) with ValueError and ensure true lexical search does not invoke dense embedding calls.
- Gracefully map default hybrid search requests to semantic search on dense-only vector stores.
- Update SearchInspector UI component to fetch backend capabilities and gate search mode buttons and weighting controls accordingly.
- Set asyncio_default_fixture_loop_scope in pytest.ini to resolve pytest-asyncio deprecation warning in CI.
- Add backend-specific test coverage for capability reporting, search mode validation, and dense/lexical/hybrid behavior across Qdrant, Chroma, and PgVector.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
@spelech

spelech commented Oct 28, 2026

Copy link
Copy Markdown
Owner Author

@jules Please review and address the following items for this PR:

Issues to Fix

  1. CRITICAL BUILD DESYNC - Rebuild Frontend Distribution Assets:
    • frontend/src/SearchInspector.tsx was modified, but the compiled assets in frontend/dist/ were not rebuilt.
    • Run npm run build inside frontend/ and commit the updated frontend/dist/ bundle so the UI reflects the changes in production builds.
  2. Requirement Traceability:
    • Tag tests in tests/backend/test_vector_store_chroma.py and tests/test_pgvector_store.py with @pytest.mark.requirement("SEARCH-CAPS-01").
    • Update docs/REQUIREMENTS.md.

How to Confirm the Fix

Run the following commands to confirm everything passes:

cd frontend && npm run build && git status
pytest tests/backend/test_vector_store_chroma.py tests/test_pgvector_store.py -v
python3 scripts/generate_requirements.py
pytest tests/backend/test_requirements_sync.py

spelech and others added 4 commits October 28, 2026 01:55
- Add get_capabilities() to VectorStore base class and implementations in QdrantVectorStore, ChromaVectorStore, and PgVectorStore.
- Include capabilities in stats and vector store config API payloads.
- Explicitly reject unsupported search modes (e.g. lexical on Chroma or pgvector) with ValueError and ensure true lexical search does not invoke dense embedding calls.
- Gracefully map default hybrid search requests to semantic search on dense-only vector stores.
- Update SearchInspector UI component to fetch backend capabilities and gate search mode buttons and weighting controls accordingly.
- Set asyncio_default_fixture_loop_scope in pytest.ini to resolve pytest-asyncio deprecation warning in CI.
- Add backend-specific test coverage for capability reporting, search mode validation, and dense/lexical/hybrid behavior across Qdrant, Chroma, and PgVector.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
- Add get_capabilities() to VectorStore base class and implementations in QdrantVectorStore, ChromaVectorStore, and PgVectorStore.
- Include capabilities in stats and vector store config API payloads.
- Explicitly reject unsupported search modes (e.g. lexical on Chroma or pgvector) with ValueError and ensure true lexical search does not invoke dense embedding calls.
- Gracefully map default hybrid search requests to semantic search on dense-only vector stores.
- Update SearchInspector UI component to fetch backend capabilities and gate search mode buttons and weighting controls accordingly.
- Set asyncio_default_fixture_loop_scope in pytest.ini to resolve pytest-asyncio deprecation warning in CI.
- Add backend-specific test coverage for capability reporting, search mode validation, and dense/lexical/hybrid behavior across Qdrant, Chroma, and PgVector.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
- Add get_capabilities() to VectorStore base class and implementations in QdrantVectorStore, ChromaVectorStore, and PgVectorStore.
- Include capabilities in stats and vector store config API payloads.
- Explicitly reject unsupported search modes (e.g. lexical on Chroma or pgvector) with ValueError and ensure true lexical search does not invoke dense embedding calls.
- Gracefully map default hybrid search requests to semantic search on dense-only vector stores.
- Update SearchInspector UI component to fetch backend capabilities and gate search mode buttons and weighting controls accordingly.
- Set asyncio_default_fixture_loop_scope in pytest.ini to resolve pytest-asyncio deprecation warning in CI.
- Add dispose_global_engine() in database engine and cleanup in temp_mcp_db fixture to prevent SQLite database lock contention in CI.
- Add backend-specific test coverage for capability reporting, search mode validation, and dense/lexical/hybrid behavior across Qdrant, Chroma, and PgVector.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
@spelech
spelech merged commit 09d2fea into main Oct 28, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix(search): expose backend capabilities instead of ignoring lexical and hybrid modes

1 participant